home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19981211-19990422
/
000352_news@watsun.cc.columbia.edu _Sun Mar 14 00:45:02 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-04-21
|
2KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id AAA26394
for <kermit.misc@watsun.cc.columbia.edu>; Sun, 14 Mar 1999 00:44:58 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id AAA09722
for kermit.misc@watsun.cc.columbia.edu; Sun, 14 Mar 1999 00:15:19 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: paul@tc.fluke.com (Paul Lutt)
Subject: Problem with K95 Alarm Problem
Date: 9 Mar 1999 07:44:34 -0800
Organization: Fluke Corporation, Everett, WA
Message-ID: <7c3fl2$oq2$1@roslyn.tc.fluke.com>
To: kermit.misc@watsun.cc.columbia.edu
I would like to use K95 kermit on NT to log some info to a file and
periodically rollover the log file every night. I put together a script
that opens a session log, sets an alarm for 00:05:00 and then loops,
waiting for input. The script is shown below.
My problem is that the alarm never seems to trigger. I've tried
changing the alarm time to something an hour or so ahead of when I start
the script and that works OK. However, I have not been able to get the
alarm to trigger with the 00:05:00 setting.
I am running version 1.1.17 of K95. I notice that there is a bug fix in
an earlier version of K95 for alarm problems at midnight, but that fix
should be in the version I'm using.
Any ideas why this isn't working?
--
Paul Lutt
Fluke Corporation
(425) 356-5059
paul@tc.fluke.com
;
; logger.ksc - log com2 data to a file
;
set port com2
if fail end 1 SET PORT failed
set speed 9600
set parity none
set flow none
while true {
log session c:/kermit/\v(ndate) append
set alarm 00:05:00
while not alarm {
input 10 \13
if failure end 1
}
close session
}